FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.7.16  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.uv.phrsfmr2#current (31 ms)

Package hl7.ehrs.uv.phrsfmr2
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.6.7.html
Url http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.6.7
Version 2.0.1-ballot
Status active
Date 2025-04-03T15:15:30+00:00
Name PH_6_7_Patient_Specific_Care__Instructions__Care_Plans__Treatment_Plans__Guidelines_and_Protocols
Title PH.6.7 Patient-Specific Care, Instructions, Care Plans, Treatment Plans, Guidelines and Protocols (Function)
Experimental False
Authority hl7
Description The system should facilitate the development of provider-generated care plans and the capture of provider-generated discharge instructions, and facilitate their capture and integration by the PHR-S.
Purpose The provider may develop and recommend a specific care plan and/or treatment plan that is tailored to the PHR Account Holder's particular circumstances including information in his or her PHR-S. The care plan and/or treatment plan may require input from several providers developed over multiple encounters. This includes enabling authorized Health Care Provider(s) to generate, communicate and record specific instructions, including discharge instructions, instructions about diet, clothing, transportation assistance, convalescence, follow-up with physician, and other related instructions. Types of providers that may offer instructions include: medical provider, social worker, physical therapist, respiratory therapist, occupational therapist, pharmacist, or a nurse.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

The system should facilitate the development of provider-generated care plans and the capture of provider-generated discharge instructions, and facilitate their capture and integration by the PHR-S.

Description I:

The provider may develop and recommend a specific care plan and/or treatment plan that is tailored to the PHR Account Holder's particular circumstances including information in his or her PHR-S. The care plan and/or treatment plan may require input from several providers developed over multiple encounters. This includes enabling authorized Health Care Provider(s) to generate, communicate and record specific instructions, including discharge instructions, instructions about diet, clothing, transportation assistance, convalescence, follow-up with physician, and other related instructions. Types of providers that may offer instructions include: medical provider, social worker, physical therapist, respiratory therapist, occupational therapist, pharmacist, or a nurse.

Actors:
ehr
Criteria N:
PH.6.7#01 SHALL

The system SHALL provide the ability to capture externally-sourced instructions or references to documents containing those instructions. Examples of instructions include: Patient-specific Care Instructions, Discharge Instructions, Treatment Plan instructions, Guidelines and/or Protocols, ad hoc instructions that were created by the provider, or institutional educational/instructional materials. Examples of externally-sourced instructions might include: documents, websites, pictures, videos, and/or sounds.

PH.6.7#02 conditional MAY

IF the system has captured externally-sourced instructions or references to documents containing those instructions, THEN the system MAY provide the ability to integrate those instructions as business rules and/or workflow rules. Examples of instructions include: Patient-specific Care Instructions, Discharge Instructions, Treatment Plan instructions, Guidelines and/or Protocols, ad hoc instructions that were created by the provider, or institutional educational/instructional materials. Examples of externally-sourced instructions might include: documents, websites, pictures, videos, and/or sounds.

PH.6.7#03 SHOULD

The system SHOULD provide the ability to capture details on further care (such as follow up, return visits, and appropriate timing of further care).

PH.6.7#04 SHOULD

The system SHOULD provide the ability to analyze and present abnormal trends with respect to the PHR Account Holder's expected or desired health or wellness outcomes (e.g., the PHR Account Holder could be alerted that the care plan anticipates a weight reduction of 1/2 pound (0.2 kg) per week, but the PHR Account Holder is actually gaining weight; or that blood glucose levels have exceeded 150 milligrams per deciliter for more than one week).

PH.6.7#05 MAY

The system MAY provide the ability to update site-specific and PHR Account Holder care plans and guidelines (e.g., isometric exercises in office versus swimming in home pool).

PH.6.7#06 MAY

The system MAY provide the ability for the PHR Account Holder to capture and maintain site-specific and PHR Account Holder care plans and guidelines (e.g., isometric exercises in office versus swimming in home pool).

PH.6.7#07 MAY

The system MAY determine, track and render alerts, notifications and reports about variances from care plans, guidelines, and discharge instructions. For example, a PHR Account Holder Representative could receive a text message notification, indicating that the PHR Account Holder failed to acknowledge compliance with a certain care plan, guideline, or discharge instruction.


Source

{
  "resourceType" : "Requirements",
  "id" : "PHRSFMR2-PH.6.7",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>The system should facilitate the development of provider-generated care plans and the capture of provider-generated discharge instructions, and facilitate their capture and integration by the PHR-S.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The provider may develop and recommend a specific care plan and/or treatment plan that is tailored to the PHR Account Holder's particular circumstances including information in his or her PHR-S. The care plan and/or treatment plan may require input from several providers developed over multiple encounters. This includes enabling authorized Health Care Provider(s) to generate, communicate and record specific instructions, including discharge instructions, instructions about diet, clothing, transportation assistance, convalescence, follow-up with physician, and other related instructions. Types of providers that may offer instructions include: medical provider, social worker, physical therapist, respiratory therapist, occupational therapist, pharmacist, or a nurse.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.7#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture externally-sourced instructions or references to documents containing those instructions. Examples of instructions include: Patient-specific Care Instructions, Discharge Instructions, Treatment Plan instructions, Guidelines and/or Protocols, ad hoc instructions that were created by the provider, or institutional educational/instructional materials. Examples of externally-sourced instructions might include: documents, websites, pictures, videos, and/or sounds.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.7#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the system has captured externally-sourced instructions or references to documents containing those instructions, THEN the system MAY provide the ability to integrate those instructions as business rules and/or workflow rules. Examples of instructions include: Patient-specific Care Instructions, Discharge Instructions, Treatment Plan instructions, Guidelines and/or Protocols, ad hoc instructions that were created by the provider, or institutional educational/instructional materials. Examples of externally-sourced instructions might include: documents, websites, pictures, videos, and/or sounds.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.7#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture details on further care (such as follow up, return visits, and appropriate timing of further care).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.7#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to analyze and present abnormal trends with respect to the PHR Account Holder's expected or desired health or wellness outcomes (e.g., the PHR Account Holder could be alerted that the care plan anticipates a weight reduction of 1/2 pound (0.2 kg) per week, but the PHR Account Holder is actually gaining weight; or that blood glucose levels have exceeded 150 milligrams per deciliter for more than one week).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.7#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to update site-specific and PHR Account Holder care plans and guidelines (e.g., isometric exercises in office versus swimming in home pool).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.7#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability for the PHR Account Holder to capture and maintain site-specific and PHR Account Holder care plans and guidelines (e.g., isometric exercises in office versus swimming in home pool).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.6.7#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY determine, track and render alerts, notifications and reports about variances from care plans, guidelines, and discharge instructions. For example, a PHR Account Holder Representative could receive a text message notification, indicating that the PHR Account Holder failed to acknowledge compliance with a certain care plan, guideline, or discharge instruction.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "extension" : [
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode" : "ehr"
    }
  ],
  "url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.6.7",
  "version" : "2.0.1-ballot",
  "name" : "PH_6_7_Patient_Specific_Care__Instructions__Care_Plans__Treatment_Plans__Guidelines_and_Protocols",
  "title" : "PH.6.7 Patient-Specific Care, Instructions, Care Plans, Treatment Plans, Guidelines and Protocols (Function)",
  "status" : "active",
  "date" : "2025-04-03T15:15:30+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "The system should facilitate the development of provider-generated care plans and the capture of provider-generated discharge instructions, and facilitate their capture and integration by the PHR-S.",
  "purpose" : "The provider may develop and recommend a specific care plan and/or treatment plan that is tailored to the PHR Account Holder's particular circumstances including information in his or her PHR-S. The care plan and/or treatment plan may require input from several providers developed over multiple encounters. This includes enabling authorized Health Care Provider(s) to generate, communicate and record specific instructions, including discharge instructions, instructions about diet, clothing, transportation assistance, convalescence, follow-up with physician, and other related instructions. Types of providers that may offer instructions include: medical provider, social worker, physical therapist, respiratory therapist, occupational therapist, pharmacist, or a nurse.",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-PH.6.7-01",
      "label" : "PH.6.7#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to capture externally-sourced instructions or references to documents containing those instructions. Examples of instructions include: Patient-specific Care Instructions, Discharge Instructions, Treatment Plan instructions, Guidelines and/or Protocols, ad hoc instructions that were created by the provider, or institutional educational/instructional materials. Examples of externally-sourced instructions might include: documents, websites, pictures, videos, and/or sounds."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-PH.6.7-02",
      "label" : "PH.6.7#02",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : true,
      "requirement" : "IF the system has captured externally-sourced instructions or references to documents containing those instructions, THEN the system MAY provide the ability to integrate those instructions as business rules and/or workflow rules. Examples of instructions include: Patient-specific Care Instructions, Discharge Instructions, Treatment Plan instructions, Guidelines and/or Protocols, ad hoc instructions that were created by the provider, or institutional educational/instructional materials. Examples of externally-sourced instructions might include: documents, websites, pictures, videos, and/or sounds."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-PH.6.7-03",
      "label" : "PH.6.7#03",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to capture details on further care (such as follow up, return visits, and appropriate timing of further care)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-PH.6.7-04",
      "label" : "PH.6.7#04",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to analyze and present abnormal trends with respect to the PHR Account Holder's expected or desired health or wellness outcomes (e.g., the PHR Account Holder could be alerted that the care plan anticipates a weight reduction of 1/2 pound (0.2 kg) per week, but the PHR Account Holder is actually gaining weight; or that blood glucose levels have exceeded 150 milligrams per deciliter for more than one week)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-PH.6.7-05",
      "label" : "PH.6.7#05",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability to update site-specific and PHR Account Holder care plans and guidelines (e.g., isometric exercises in office versus swimming in home pool)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-PH.6.7-06",
      "label" : "PH.6.7#06",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability for the PHR Account Holder to capture and maintain site-specific and PHR Account Holder care plans and guidelines (e.g., isometric exercises in office versus swimming in home pool)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "PHRSFMR2-PH.6.7-07",
      "label" : "PH.6.7#07",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY determine, track and render alerts, notifications and reports about variances from care plans, guidelines, and discharge instructions. For example, a PHR Account Holder Representative could receive a text message notification, indicating that the PHR Account Holder failed to acknowledge compliance with a certain care plan, guideline, or discharge instruction."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.